G400E - hanging up?

CLI output:

2:<<< 0 AT+CSQ -- +CLIP: "94xxxxxx",129,"",,"",0 , 30
-- Accepting call from '94xxxxxx' to 's' on channel 1, span 2
-- Executing [s@from-gsm-200:1] Answer("EXTRA/3-1", "") in new stack
-- Executing [s@from-gsm-200:2] Dial("EXTRA/3-1", "SIP/200") in new stack
== Using SIP RTP CoS mark 5
-- Called SIP/200
-- SIP/200-0000003d is ringing
2:<<< 0 ATA -- OK , 2
2:<<< 0 ATA -- +CSQN: 17, 7 , 12
1:<<< 0 AT+CLVL? -- +CSQN: 27, 0 , 12
2:<<< 0 ATA -- +CSQN: 16, 5 , 12

Now I call to a second number:

2:<<< 0 ATA -- +CSQN: 15, 6 , 12
2:<<< 0 ATA -- +CSQN: 13, 7 , 12
2:<<< 0 ATA -- +CSQN: 16, 7 , 12
2:<<< 0 ATA -- +CSQN: 15, 7 , 12
2:<<< 0 ATA -- +CSQN: 16, 7 , 12
2:<<< 0 ATA -- +CSQN: 14, 7 , 12
2:<<< 0 ATA -- +CSQN: 16, 7 , 12
2:<<< 0 ATA -- +CSQN: 15, 7 , 12
2:<<< 0 ATA -- +CSQN: 16, 7 , 12
1:<<< 0 AT+CLVL? -- +CSQN: 28, 0 , 12
2:<<< 0 ATA -- +CSQN: 14, 7 , 12
2:<<< 0 ATA -- +CSQN: 16, 7 , 12
-- SIP/200-0000003d answered EXTRA/3-1
2:<<< 0 ATA -- +CSQN: 15, 7 , 12

On the second phone I hear standard waiting tone (not aswered by Asterisk). I disconnect a second (not first) connection and that happens:

2:<<< 0 ATA -- +CSQN: 14, 7 , 12
2:<<< 0 ATA -- NO CARRIER , 10
-- Channel 1, span 2 got hangup, cause 16
== Spawn extension (from-gsm-200, s, 2) exited non-zero on 'EXTRA/3-1'
-- Hungup 'EXTRA/3-1'
2:<<< 0 AT+CSQ -- +CSQ: 14,7 , 10
2:<<< 1 AT+CSQ -- OK , 2
2:<<< 0 AT+CSQ -- +CSQN: 15, 7 , 12
2:<<< 0 AT+CSQ -- +CSQN: 16, 7 , 12
2:<<< 0 AT+CSQ -- +CSQN: 17, 5 , 12
2:<<< 0 AT+CSQ -- NO CARRIER , 10
[Jun 17 20:07:35] WARNING[3080]: chan_extra.c:7316 gsm_dchannel: Hangup requested on unconfigured channel 255/255 span 2
2:<<< 0 AT+CSQ -- +CSQN: 26, 0 , 12
2:<<< 0 AT+CSQ -- +CSQN: 27, 0 , 12
1:<<< 0 AT+CLVL? -- +CSQN: 27, 0 , 12
1:<<< 0 AT+CLVL? -- +CSQN: 28, 0 , 12

What's wrong?

Hi,
Please show me your OS and software version.(OS,asterisk,dahdi,chan-extra)

CentOS - 6.4 (final)
Kernel - 2.6.32-358.6.2.el6.i686
Asterisk - 1.8.18.1
Dahdi - 2.6.2
Chan_extra - 2.0.7


Update 1:

I've forgotten to mention that both SIM cards have the same phone number.

For now I've noticed that "call waiting" feature is switched on somewhere. But I don't have idea where to look for it. I have already changed settings in chan_extra.conf and chan_dahdi.conf.

I've made some more research:
When the first call is in progress and someone else try to call me, than I hear a signal about second incoming call. On the same time, second caller hear a standard (not asterisk) waiting tone.
Now, the worst thing: if second caller hungs up, than first connection is also disconected (as showed in post #2).
If the first caller hungs up, while a second one tries to reach me, than he is connected with me (see below).


CLI output:

-- Accepting call from '94xxxxxx' to 's' on channel 1, span 2
-- Executing [s@from-gsm-200:1] Answer("EXTRA/3-1", "") in new stack
-- Executing [s@from-gsm-200:2] Dial("EXTRA/3-1", "SIP/200") in new stack
== Using SIP RTP CoS mark 5

In the meantime I call from a second phone.

-- Called SIP/200
-- SIP/200-00000015 is ringing

I have decided to stop first call:

-- Channel 1, span 2 got hangup, cause 16
== Spawn extension (from-gsm-200, s, 2) exited non-zero on 'EXTRA/3-1'
-- Hungup 'EXTRA/3-1'

Now asterisk reacts on the second call:

-- Accepting call from '40xxxxxx' to 's' on channel 1, span 2
-- Executing [s@from-gsm-200:1] Answer("EXTRA/3-1", "") in new stack
-- Executing [s@from-gsm-200:2] Dial("EXTRA/3-1", "SIP/200") in new stack
== Using SIP RTP CoS mark 5
-- Called SIP/200
-- SIP/200-00000016 is ringing
-- Channel 1, span 2 got hangup, cause 16
== Spawn extension (from-gsm-200, s, 2) exited non-zero on 'EXTRA/3-1'
-- Hungup 'EXTRA/3-1'


Update 2:

I've tried to send AT commands: gsm send at 1 "AT+CCWA=0", but it doesn't helped.


i] Last edited by RTurala at 2013-6-18 14:17 [/i

Hi,
Now the driver chan-extra is not support the "call waiting" feature, you should turn off this feature!

I would like to, but how can I do that? Maybe that's made by operator... I'll check that.

Hi,
Yes, you can ask your operator to disable this feature.